@brettsam You need to add a dependency on Microsoft.Azure.Functions.Worker version 1.8.0 or higher, as this code crashes when using Microsoft.Azure.Functions.Worker version 1.6.0 with the following exception
System.MissingMethodException: 'Method not found: 'Microsoft.Extensions.DependencyInjection.IServiceCollection Microsoft.Extensions.DependencyInjection.ServiceCollectionExtensions.RegisterDefaultConverters(Microsoft.Extensions.DependencyInjection.IServiceCollection)'.'

For me this works in general but I still have difficulties getting logs from the isolated worker with a level lower than Warning.
I understand that this now needs to be controlled separately from host.json and therefore tried to controll via appsettings.json:

           var host = new HostBuilder()
                .ConfigureAppConfiguration(c =>
                {
                    c.AddJsonFile("appsettings.json", optional: true, reloadOnChange: true);
                    c.AddJsonFile("local.settings.json", optional: true, reloadOnChange: true);
                    c.AddEnvironmentVariables();
                    c.Build();
                })
                .ConfigureFunctionsWorkerDefaults(builder =>
                {
                        builder
                        .AddApplicationInsights()
                        .AddApplicationInsightsLogger();

                })

appsettings.json has the same settings like host.json which work perfectly for the host.

Inside the worker I tried logging to a ILoggerFactory via DI and also via the FunctionContext.GetLogger().

            _logger.LogWarning("LogWarning Test");
            _logger.LogInformation("LogInformation Test");

The first one comes through, the second one not.

@Done3319 try #1123 (comment) (or #1123 (comment))

Hello,

I was trying to used isolated function to run Availability test.
I had an issue following as Activity.Current was being null if using packages:
-Microsoft.Extensions.Logging.ApplicationInsights 2.21.0
-Microsoft.ApplicationInsights.WorkerService 2.21.0
I tried to make something with functionContext, but unsuccessfully, and finally went to this package and it worked.

But i already new this package and discarded it in the past for other function as i needed scope logs and its hardcoded in src/DotNetWorker.ApplicationInsights/FunctionsApplicationInsightsExtensions.cs
logging.AddApplicationInsights(options => { options.IncludeScopes = false; configureOptions?.Invoke(options); });

My question is then (probably @brettsam) is there a reason why this is harcoded?

Hi @brettsam, is there a reason why TelemetryClient isn't registered as singleton? Doing so would allow us to resolve that dependency and start tracking events. The scenario I see is to track retries and single successful runs for Azure Service Bus triggers.

Right now https://github.com/Azure/azure-functions-dotnet-worker/blob/main/src/DotNetWorker.ApplicationInsights/FunctionsTelemetryModule.cs creates a TelemetryClient. I see no reason why this dependency can't be registered as singleton.

https://github.com/Azure/azure-functions-dotnet-worker/blob/main/src/DotNetWorker.ApplicationInsights/FunctionsApplicationInsightsExtensions.cs alsready registers the module as singleton.

Or are you worried that someone already registered the TelemetryClient and that's why you would like an instance of "your own"?

TelemetryClient is registered as a singleton by App Insights already -- https://github.com/microsoft/ApplicationInsights-dotnet/blob/main/NETCORE/src/Shared/Extensions/ApplicationInsightsExtensions.cs#L365. You can use it in any class constructor and see for yourself.

We're doing nothing special with App Insights types or registrations. We call AddApplicationInsightsTelemetryWorkerService() and that SDK handles everything. So in general, if it works in some other project, it'll work here.

As for why the module uses its own client -- I was following the patterns of other modules. (https://github.com/microsoft/ApplicationInsights-dotnet/blob/main/WEB/Src/Web/Web/ExceptionTrackingTelemetryModule.cs)

I seem to recall that during testing this, the modules have some circular dependency issues and you can't inject the client there. I think it's b/c the TelemetryClient depends on TelemetryConfiguration, which calls Initialize() on all modules. I just tried it quickly in a test and got a stack overflow. So that's very specific to TelemetryModules and how they work.

Yes, I discovered that this afternoon: once I include and enable the Functions AI package, I can resolve the TelemetryClient.

@brettsam given this is merged, what are the plane to actually release theMicrosoft.Azure.Functions.Worker.ApplicationInsights package?

Hi @brettsam ,
Is it still possible to use TelemetryClient instead of logging when sending Telemetry data to Azure in isolated Azure Functions?
Our platform has many submodules that use TelemetryClient without Dependency Injection, which is created through a static initializer, using APPINSIGHTS_INSTRUMENTATIONKEY.
As our new Azure (Service Bus Listeners) Functions are dotnet-isolated, the TelemetryClient doesn't send telemetry data anymore. The content in the traces table lacks some important data, for example, operationName, customDimensions (like Function Invocation Id) and synthetic source, among other things.
If we use logging, then the data is sent correctly, however, if we want to re-implement our telemetry mechanism using logging and DI, it will require a massive overhaul and we would lose some features like metrics etc.
Previously, when using TelemetryClient, it would populate everything automatically (in a non-isolated function), but now it seems that I have to set all these parameters manually, or I'm doing something wrong when configuring Logging.

My Program.cs is defined as:

var host = Host.CreateDefaultBuilder()
.ConfigureFunctionsWorkerDefaults(builder => builder.AddApplicationInsights().AddApplicationInsightsLogger())
.ConfigureServices() // our Singletons
.Build();

await host.RunAsync();

and our packages are:

<PackageReference Include="Microsoft.ApplicationInsights.WorkerService" Version="2.21.0" />
<PackageReference Include="Microsoft.Azure.Functions.Worker.ApplicationInsights" Version="1.0.0-preview4" />
<PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="1.11.0" />
<PackageReference Include="Newtonsoft.Json" Version="13.0.3" />
<PackageReference Include="System.Net.NameResolution" Version="4.3.0" />
<PackageReference Include="Microsoft.Azure.Functions.Extensions" Version="1.1.0" />
<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.ServiceBus" Version="5.11.0" />
<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http" Version="3.0.13" />
<PackageReference Include="Microsoft.Azure.Functions.Worker" Version="1.16.0" />
<PackageReference Include="Microsoft.NETCore.Targets" Version="5.0.0" />

Would you have an idea if I need to add some extra config or something else?